Version management errors will be displayed in an Application Download Results dialog box showing the particular error encountered. Error messages will contain an error number, shown as (%d) below, or the path\file shown as '%s' below. Depending on the error you may be able to launch the application anyway.
See the following sections for an explanation of common version management errors:
| Error Message | Description/Resolution |
|---|---|
|
Error (%d) occurred while downloading '%s'. |
Either the file was not uploaded to the BLOB or the user does not have at least "Read" authorization for the BSS. Check the file to make sure it resides in the correct group in the BSS from which the user is performing version management. If the file is there, check security to make sure the user has at least "Read" authorization for the BSS. |
|
The specified blob file '%s' could not be found for download. |
The file could not be found in the BSS. Verify that the file resides in the specified group in the BSS from which the user is performing version management. |
|
No need to download file '%s'. |
|
|
The specified file '%s' does not need updating. |
|
|
The specified file '%s' already exists. Add new not performed. |
The current version of the file exists on the local drive. |
|
Download of blob file '%s' canceled by user. |
User canceled version management before operation completed. |
|
Access denied to file '%s'. Is file in use? |
The file is in use and cannot be replaced. Close any applications that may be using the file and restart the application using the Version Manager. |
|
Application download failed. |
Application download failed. |
|
Unknown exception caught while downloading '%s'. |
Unknown exception. |
| Error Message | Description/Resolution |
|---|---|
|
Maximum chained RSP file depth of 20 exceeded. |
Maximum number of .rsp files that can be daisy chained is 20 or there is a circular reference in those chained. |
|
Could not open response file. |
The .rsp file could not be found in the BSS or it may be corrupt. Reload file to the BSS. |
|
Failed to parse response file entry: '%s'. |
The .rsp file may contain an invalid entry. Check syntax and punctuation of each line. Ensure that the pound sign (#) proceeds comment lines. |
| Error Message | Description/Resolution |
|---|---|
|
VsiError caught while downloading '%s' - DCL error (-9) 'The CygNet service <service name> is not in service. |
The BSS from which the application was installed is out of service or has failed. Restart the BSS. To change the BSS from which version management is run, reinstall the application or manually edit the Start menu shortcut. |
|
The database index for service '%s' is out of date and must be reindexed. |
The index of the BSS is not valid. Use the ReIndexESE utility to create a new index for the service. |
| Error Message | Description/Resolution |
|---|---|
|
Registration of '%s' failed. Info:'%s'. |
The installation parameter of <REGISTER> was specified for the file in the .rsp, but the file could not be registered. Verify that the control can be registered using regsvr32.exe (located in the Windows\System32 folder, or use Windows\SysWOW64\regsvr32.exe on a 64-bit operating system). If so, reload the source file to the BSS. If not, remove the parameter from the .rsp. |
| Error Message | Description/Resolution |
|---|---|
|
Default CygNet install client directory not defined. |
The Client Installer has not been installed. Install the Client Installer and re-click the CygNet shortcut. |
|
ShellExec failed for '%s' '%s'. |
Attempt to run the specified file failed. Ensure file association and any specified parameters are valid. |
|
Caught exception in LaunchAppEntries. |
Exception error. |
|
|
|
